Great job! But let's fix a couple of issues:

• Let's rename "Git URL" to "Dataset repository"
• Let's don't have "Git Path" as a separate field. I propose:
  Dataset repository [ git repository url ] [ relative path to file ]
• Let's add popup hints for "git url" and "git path"
• Error handling if ssh key isn't added should be better. It will be a usual mistake. Need to ask the user to add ssh key into git server explicitly and probably show the key (otherwise the user should go into container and copy the key)

• User for commit should be changed (now it is ExampleOrgz)
• Sync status should be more visible in dashboard. I propose colored background for task item (red - unsync, yellow - sync but not merged, green - merged)

• diff file was committed into my repository. Is it expected?

• git url and path isn't dumped into the xml file itself.

• Need to provide good default value for git path (e.g. <dump file name>.xml)

@nmanovic

"Error handling if ssh key isn't added should be better. It will be a usual mistake. Need to ask the user to add ssh key into git server explicitly"
Interaction with an user during building is actually good idea?

@nmanovic
"diff file was committed into my repository. Is it expected?"
changelog_*.diff is commited to repos. It is expected. Other diffs files stores outside repository directory.

@nmanovic
"Sync status should be more visible in dashboard. I propose colored background for task item (red - unsync, yellow - sync but not merged, green - merged)"
It is very long for loading because each "get_remote_status" request does request to git server (1-3 sec). I have no idea how implement it effectively yet.

@nmanovic
Other comments have been implemented

Interaction with an user during building is actually good idea?

It isn't during building. It is when a user try to push something into a repository for which the user doesn't add generated ssh key. It will get some error that the repository cannot be cloned with a lot of extra stuff. I remember that it isn't so easy to understand why a repository cannot be cloned. Let's say that "Probably SSH key was not added to your profile for the cloned repository. Please add the key below and try again".

changelog_*.diff is commited to repos. It is expected. Other diffs files stores outside repository directory.

Why do we need it inside repository? Is it a temporary file for internal purpose?

It is very long for loading because each "get_remote_status" request does request to git server (1-3 sec). I have no idea how implement it effectively yet.

Indeed the task is very important. It is really good feature. I need it to be sure that latest tasks are synchronized and it will be inconvenient to click each time on a task to understand its status.

There are several ways to implement that:

• Just cache the latest status always and return it together with task info for dashboard. But it will necessary to click each time the task push as well. But one clicked it will be "save" state.
• Ask users to add a webhook. I don't like the approach but probably it will work best with the approach above.
• Implement a background task which sync the status time to time for non-merged repos and cache it. It will work best from my point of view. Also when a user press "push" button the status is cached as well.

@bsekachev ,

Does ssh key is regenerated each time when you re-build CVAT? If it is so need to fix that. It should be generated once as django security key. It is really a pain to add a new key each time.

@nmanovic
"Why do we need it inside repository? Is it a temporary file for internal purpose?"
No, this contains information about changed objects and dates.

@bsekachev ,

Is it possible to incorporate the information into git commit message? Why do we need a separate file for that?

@nmanovic
Please, review it again.